ci(release): token publish for first npmjs release#10
Merged
Conversation
OIDC Trusted Publishing can't create packages that don't exist on npmjs yet (@agent-ix/ix, ix-cli-local, ix-cli-elements are new). Use the NPM_TOKEN secret for this first publish; revert to trusted_publish once the packages exist and trusted publishers are configured. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
OIDC Trusted Publishing can't bootstrap packages that don't exist on npmjs yet (@agent-ix/ix, ix-cli-local, ix-cli-elements are new). Switch release.yml to token-based publishing via the NPM_TOKEN secret for the first publish; revert to trusted_publish once packages exist + trusted publishers are configured.
🤖 Generated with Claude Code